Digital rights management (drm) locker

ABSTRACT

Methods, apparatuses and storage medium associated digital rights management (DRM) using DRM locker is disclosed herein. In embodiments, a DRM locker is provided to a client device. The DRM locker may be configured to store a number of DRM licenses or keys for a number of DRM protected contents. The DRM locker, on presentation of an associated locker key, may respond to a request for one or more of the stored DRM licenses or keys, to enable consumption of the corresponding DRM protected contents using the client device. Other embodiments may be disclosed or claimed.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/566,223, entitled “Digital Rights Management (DRM) Locker,” filed onAug. 3, 2012, and claims priority to the Ser. No. 13/566,223application. The specification of the Ser. No. 13/566,223 application ishereby fully incorporated by reference.

TECHNICAL FIELD

This application relates to the technical field of data processing, morespecifically to methods, apparatuses and storage medium associateddigital rights management through usage of digital rights management(DRM) lockers.

TECHNICAL FIELD

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Unless otherwiseindicated herein, the materials described in this section are not priorart to the claims in this application and are not admitted to be priorart by inclusion in this section.

Traditionally, DRM is configured to protect content for the benefit ofthe content provider. DRM is employed to prevent the content from beingcopied, altered, or used by unauthorized parties. A content providertypically sets up DRM servers and requires the consumers validate theirlicenses with these servers every time an access to a purchased contentis needed. Each DRM scheme, often unique to a content provider, controlshow the content distributed by the content provider is consumed and whois able to consume it, protecting the rights of the content provider andenforcing the rules defined by the content provider.

The consumers of purchased contents must abide by these rules defined bythe content owners due to the various DRM schemes employed. Specificcontent consumption programs equipped to support particular DRM schemesmust be used, and there could be restrictions on what kind of devicesare allowed to consume the content. Consumers that want to consume thecontent using methods that differ from what a content provider intendedmay be prevented to do so by the DRM scheme employed. A possible usecase would be to consume the content when Internet connectivity is notavailable. Consumers that live within the boundaries that the contentprovider specifies, are free to use the content as long as the contentprovider retains the infrastructure to support the DRM scheme.

If a content provider has Internet connectivity issues, turns off theDRM servers, or stops being a content provider; the consumer can loseaccess to the purchased content from the particular content provider.Content providers have discontinued support of DRM servers in the pastwhere consumers were advised to burn their music to audio CDs before theshutdown or lose access to the purchased contents. For musical contents,the burning of an audio CD removes the DRM from the music, and theconsumer can import the music into their devices without regard for theDRM protocol established by the content provider. The problem with thisprocess is that the music is often converted from one compressed formatto another compressed format, which frequently reduces the quality ofthe music. It also allows the consumer to start using the content inways the content provider did not intend. The content creators thatlicensed the contents to the content provider could lose further salesdue to the removal of the DRM which they expected to be retained on thecontents.

Thus, the consumer is the party that is highly impacted by contentproviders' DRM schemes, and is at risk of losing access to purchasedcontent for various reasons.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will be described by way ofexemplary embodiments, but not limitations, illustrated in theaccompanying drawings in which like references denote similar elements,and in which:

FIG. 1 illustrates an overview of an arrangement associated with digitalrights management through usage of DRM lockers provided by a DRM lockervendor;

FIG. 2 illustrates an overview of the interactions between the clientdevices, the server(s) of the DRM locker vendor and optionally, theserver(s) of an escrow service provider;

FIG. 3 illustrates an example operational flow of a content distributionsystem of a content provider;

FIG. 4 illustrates an example operation flow of a DRM library on aclient device;

FIG. 5 illustrates an example operation flow of a DRM locker on a clientdevice;

FIG. 6 illustrates an example computer system suitable for use as aclient device or a server; and

FIG. 7 illustrates an example non-transitory computer-readable storagemedium having instructions configured to practice all or selectedaspects of the operational flows of FIGS. 2-5; all arranged inaccordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

Methods, apparatuses and storage medium associated with digital rightsmanagement through usage of DRM lockers is disclosed herein. Inembodiments, DRM lockers may be provided by a DRM locker vendor, whichmay be separate and/or independent of content providers. A DRM lockerprovided to a client device may be configured to locally store DRMlicenses or keys of various DRM protected contents of different contentproviders. The DRM licenses or keys may be of different license or keytypes. The employment of a DRM locker may enable a user of the clientdevice to be able to continue to enjoy and consume the DRM protectedcontents even when the DRM license or key servers of the contentproviders are no longer accessible or available. Other benefits andadvantages may also be described and/or apparent to those skilled in artfrom the description to follow.

Various aspects of the illustrative embodiments will be described usingterms commonly employed by those skilled in the art to convey thesubstance of their work to others skilled in the art. However, it willbe apparent to those skilled in the art that alternate embodiments maybe practiced with only some of the described aspects. For purposes ofexplanation, specific numbers, materials, and configurations are setforth in order to provide a thorough understanding of the illustrativeembodiments. However, it will be apparent to one skilled in the art thatalternate embodiments may be practiced without the specific details. Inother instances, well-known features are omitted or simplified in ordernot to obscure the illustrative embodiments.

Various operations will be described as multiple discrete operations, inturn, in a manner that is most helpful in understanding the illustrativeembodiments; however, the order of description should not be construedas to imply that these operations are necessarily order dependent. Inparticular, these operations need not be performed in the order ofpresentation. Further, descriptions of operations as separate operationsshould not be construed as requiring that the operations be necessarilyperformed independently and/or by separate entities. Descriptions ofentities and/or modules as separate modules should likewise not beconstrued as requiring that the modules be separate and/or performseparate operations. In various embodiments, illustrated and/ordescribed operations, entities, data, and/or modules may be merged,broken into further sub-parts, and/or omitted.

The phrase “in one embodiment” or “in an embodiment” is used repeatedly.The phrase generally does not refer to the same embodiment; however, itmay. The terms “comprising,” “having,” and “including” are synonymous,unless the context dictates otherwise. The phrase “A/B” means “A or B”.The phrase “A and/or B” means “(A), (B), or (A and B)”. The phrase “atleast one of A, B and C” means “(A), (B), (C), (A and B), (A and C), (Band C) or (A, B and C)”.

FIG. 1 illustrates an overview of an arrangement associated with digitalrights management through usage of DRM lockers, in accordance withvarious embodiments. As illustrated, arrangement 100 may include anumber of client devices 108 coupled with one or more servers 104 of aDRM locker vendor, via network(s) 110. The DRM locker vendor may beseparate and/or independent of the content providers. The DRM lockervendor may, e.g., through server(s) 104 and DRM locker service 122operated thereon, provide DRM lockers 150 to client devices 108. A userof a client device 108 may use his/her DRM locker 150 to securely storeDRM licenses or keys 152 of various DRM protected contents 148 acquiredfrom various content providers, e.g., from servers 102 of the variouscontent providers. The acquired DRM protected contents 148 may be DRMprotected audio and/or video contents. Servers 102, may likewise becoupled with server(s) 104 and client devices 108 via network(s) 110. Asdescribed earlier, employment of DRM locker 150 may provide a user of aclient device 108 with various benefits and/or advantages, including,e.g., but not limited to, the ability to continue to enjoy and consumeacquired DRM protected contents 148 even when the DRM license or keyservers of the content providers, e.g., servers 102, are no longeraccessible or available. These and other related topics will bedescribed in more detail below, with references to FIGS. 2-5.

Still referring to FIG. 1, server(s) 102 of a content provider, asillustrated, may include content distribution system 112 and DRMprotected contents 114 of the content provider available foracquisition. As will be described in more detail below, contentdistribution system 112 may be configured to cooperate to enable DRMlicenses or keys 152 employed to protect contents 114 to be stored inDRM lockers 150 of client devices 108, thereby enabling acquired DRMprotected contents 148 to be consumed legitimately, without requiringavailability or accessibility of the DRM license or key servers of thecontent providers, e.g., servers 102.

In various embodiments, DRM lockers 150 may be secured, and havecorresponding associated locker keys (not shown in FIG. 1, to bedescribed in more detail later). For these embodiments; possession ofthe associated locker keys may be required in order to be able to accessDRM licenses or keys 152 stored in DRM lockers 150. For the illustratedembodiments, arrangement 100 may further include server(s) 106 of one ormore escrow service providers, having one or more corresponding escrowservices 132 correspondingly operated thereon. Similar to therelationship between the DRM locker vendor and the content providers, anescrow service provider may likewise be separate and/or independent ofthe DRM locker vendor. Escrow service 132 of a escrow service providermay be employed to escrow the locker keys to facilitate migration of aDRM locker 150 from one of client devices 108 to another one of clientdevices 108, e.g., in a situation where a user of a client device 108wants to upgrade and/or replace his/her device. Similar to servers 102and 104 and client devices 108, server(s) 106 may be coupled withservers 102 and 104 and client devices 108 via network(s) 110.

Each client device 108, in addition to DRM locker 150, may furtherinclude a browser, a content distribution system (CDS) client, a DRMlocker service (DLS) client and/or an escrow service (ES) client,collectively denoted 142, depending on whether each of contentdistribution systems 112, DRM locker service 122 and escrow service(s)132 is configured to be accessed with a browser or a correspondingclient. For example, in embodiments, a content distribution system 112,DRM locker service 122 and/or an escrow service 132 may be a web siteconfigured to be accessed with a browser. In other embodiments, acontent distribution system 112, DRM locker service 122 and/or an escrowservice 132 may be a server application configured to interact with acorresponding client, e.g., “apps” for smartphone client devices.

Further, each client device 108 may include a media player 144 andoptionally, a DRM library 146. Each client device 108 may be, but notlimited to, a smartphone, a computing tablet, a laptop computer, adesktop computer, a personal digital assistant (PDA), a game player, amedia player, a game console, a set-top box, or other devices of thelike. Media player 144, and media library 146, when employed, areintended to represent a broad range of these elements known in the art.

Various example embodiments of computing devices suitable for use asservers 102-106 and/or client devices 108 will be described later withreferences to FIG. 6. Networks 110 are intended to represent a broadrange of wired and/or wireless, local and/or wide area, private and/orpublic networks, e.g., the Internet, known in the art.

FIG. 2 illustrates an overview of the interactions between the clientdevices, the server(s) of the DRM locker vendor and optionally, theserver(s) of an escrow service provider, in accordance with variousembodiments of the present disclosure. As illustrated, a client device108 may initially interact with DRM locker service 122, using a browseror a DLS client 142, to acquire a DRM locker 150. As described earlier,DRM locker 150 may be secured, and access to its content may beprotected by a DRM locker key 202. For the embodiments, DRM lockerservice 122 may provide a particularized copy of DRM locker key 202′ toa client device 108, as part of the initial acquisition, for use toaccess DRM locker 150 on the particular client device 108. DRM lockerkey 202′ may be particularized to a client device 108, e.g., byincorporating information into DRM locker key 202′, that are unique tothe particular client device. In various embodiments, theparticularization of a DRM locker 202′ to a particular client device maybe performed by DRM locker service 122 before provided to the clientdevice 108, or by DRM locker 150, e.g., through localization, afterprovision to the client device 108. In alternate embodiments, otherapproaches to secure DRM locker 150 may be employed instead. Inembodiments, DRM locker service 122 may provide DRM locker key 202′ toDRM library 146 or media player 144 of client device 108, depending onimplementation preference.

Further, in embodiments, as part of the acquisition process, or shortlythereafter, DRM locker service 122 may provide a master copy of DRMlocker key 202 to an escrow service 132 for safe keeping. At asubsequent point in time, when the user of a client device 108 needs toreplace the client device 108, the user may load a backup copy 204 ofthe software and data content of the client device 108 onto thereplacement client device 108′. Upon loading the backup copy, the usermay, e.g., use a browser or an ES client 142 to contact a correspondingescrow service 132 to obtain a new copy of DRM locker key 202″particularized to the replacement client device 108′. In embodiments,the escrow service 132 may provide the replacement client device 108′with the new DRM locker key 202″ after receiving the appropriatelicensee account and/or authentication information, as well asinformation about the replacement client device 108′. As with theinitial DRM locker key 202′, DRM locker key 202″ may be particularizedto the replacement client device 108′ by the escrow service 132 or bythe DRM locker 150 on the replacement client device 108′. Inembodiments, the escrow service 132 may limit the number of replacementDRM locker keys 202″ that may be issued.

FIG. 3 illustrates an example operational flow of a content distributionsystem of a content provider, in accordance with various embodiments ofthe present disclosure. As shown, operational flow 300 may start atblock 302, with the content distribution system 112 receiving a purchaseorder for a DRM protected content of the content provider from a clientdevice 108. As described earlier, the purchase order may be receivedfrom a browser or a CDS client 142 of the client device 108. On receiptof the purchase order, flow 300 may proceed from block 302 to block 304.At block 304, the content distribution system 112 may determine whetherthe client device 108 has a DRM locker 150.

If it is determined that client device 108 has a DRM locker 150, flow300 may proceed from block 304 to block 306. At block 306, the contentdistribution system 112 may generate a DRM license or key for the DRMprotected content being purchased, designed for local use by the user ofthe client device 108. From block 306, flow 300 may proceed to block308. At block 308, the content distribution system 112 may provide thelocal DRM license or key to the DRM locker 150 on the client device 108.

On the other hand, if it is determined that the client device 108 doesnot have a DRM locker 150, flow 300 may proceed from block 304 to block310 instead. At block 310, the content distribution system 112 maygenerate a DRM license or key for the DRM protected content beingpurchased, designed for network use by the user of the client device108. That is, the client device 108 has to contact the contentdistribution system 112 when the user desires to consume the DRMprotected content. From block 310, flow 300 may proceed to block 312. Atblock 312, the content distribution system 112 may store the network DRMlicense or key for future use by the client device 108.

Either case, from block 306 or 312, flow 300 may proceed to block 314.At block 314, the content distribution system 112 may download the DRMprotected content 114 to the client device 108, and store as acquiredDRM protected content 148 on the client device 108.

FIG. 4 illustrates an example operation flow of a DRM library on aclient device, in accordance with various embodiments of the presentdisclosure. As illustrated, operational flow 400 may start at block 402.At block 402, DRM library 146 on a client device may receive a requestfor DRM protected content. For example, DRM library 146 may receive sucha request from media player 144. Media player 144 may make the requestin response to a user's request to play the DRM protected content.

From block 402, flow 400 may proceed to block 404. At block 404, DRMlibrary 146 may determine whether the client device 108 has a DRM locker150. On determining that the client device 108 has a DRM locker 150,flow 400 may proceed from block 404 to block 406. At block 406, DRMlibrary 146 may confirm and/or obtain the local DRM license or key 152from DRM locker 150. On the other hand, if it is determined that theclient device 108 does not have a DRM locker 150, flow 400 may proceedfrom block 404 to block 408. At block 408, DRM library 146 may confirmand/or obtain the network DRM license or key from content distributionsystem 112. In embodiments, DRM library 146 may first determine whetherthe client device 108 is connected to network(s) 110. If client device108 is not connected to network(s) 110, DRM library 146 may respond tothe request with an error, indicating, e.g., requested content notavailable.

Either case, from block 406 or 408, flow 400 may proceed to block 410.At block 410, DRM library 146 may unprotect, e.g., decrypt, the content,and respond to the request with the unprotected content.

As alluded to earlier, in alternate embodiments, flow 400 may beintegrated with and performed by media player 144.

FIG. 5 illustrates an example operation flow of the DRM locker on aclient device; in accordance with various embodiments of the presentdisclosure. As illustrated, operational flow 500 may start at block 502.At block 502, e.g., during the purchase of a DRM protected content, DRMlocker 150 on a client device may receive a request from a contentdistribution system 112 to confirm the existence of DRM locker 150, andin response, provide the requisite identification and/or authenticationinformation of the client device 108 and/or the user. From block 502,flow 500 may proceed to block 504. At block 504, DRM locker 150 mayprovide the requested identification and/or authentication informationto content distribution system 112. In embodiments, DRM locker 150 mayprovide the requested identification and/or authentication information,after content distribution system 112 has identified and/orauthenticated itself.

From block 504, flow 500 may proceed to block 506. At block 506, DRMlocker 150 may receive one or more DRM licenses or keys for one or moreDRM protected contents from content distribution system 112, and storethe received DRM licenses or keys. From block 504, flow 500 may returnto block 502, where the flow may be repeated again with contentdistribution system 112 of the same content provider or differentcontent providers. The different content providers may be interactedusing browser or different CDS clients 142. Accordingly, as describedearlier, DRM locker 150 may store DRM licenses or keys 152 of differenttypes, for different DRM protected contents from the same or differentcontent providers.

At block 506, flow 500 may proceed to block 508 instead. At block 508,DRM locker 150 may receive a request for DRM license or key for a DRMprotected content. For example, DRM locker 150 may receive the requestfrom DRM library 146. From block 508, flow 500 may proceed to block 510.At block 510, DRM locker 150 may determine whether it has the DRMlicense or key for the DRM protected content of interest. If it isdetermined that DRM locker 150 has the DRM license or key for the DRMprotected content of interest, flow 500 may proceed to block 512. Atblock 512, DRM locker 150 may confirm and/or retrieve and return the DRMlicense or key, so it can be used to unprotect the content, and enablethe unprotected content to be available. On the other hand, if it isdetermined that DRM locker 150 does not have the DRM license or key forthe DRM protected content of interest, flow 500 may proceed to block514. At block 514, DRM locker 150 may return an error, indicating, e.g.,the DRM protected content is not available.

Either case, from block 512 or 514, flow 500 may proceed to block 516.At block 516, flow 500 may transition to block 502 on another requestfrom a content distribution system 112, or to block 508 on anotherrequest for DRM license or key.

FIG. 6 illustrates an example computer system suitable for use as aclient device or a server, in accordance with various embodiments of thepresent disclosure. As shown, computer 600 may include a number ofprocessors or processor cores 602, and system memory 604. For thepurpose of this application, including the claims, the terms “processor”and “processor cores” may be considered synonymous, unless the contextclearly requires otherwise. Additionally, computer 600 may include massstorage devices 606 (such as diskette, hard drive, compact disc readonly memory (CD-ROM) and so forth), input/output devices 608 (such asdisplay, keyboard, cursor control and so forth) and communicationinterfaces 610 (such as network interface cards, modems and so forth).The elements may be coupled to each other via system bus 612, which mayrepresent one or more buses. In the case of multiple buses, they may bebridged by one or more bus bridges (not shown).

The elements included, and their capacity or performance characteristicsmay vary depending on whether example computer system 600 is employed asone of servers 102-106 or one of client devices 108.

Each of the elements may perform its conventional functions known in theart. In particular, system memory 604 and mass storage 606 may beemployed to store a working copy and a permanent copy of the programminginstructions implementing the various ones of the elements, such ascontent distribution system 112, DRM locker service 122, escrow service132, media player 144, DRM library 146, DRM locker 150 (or portionthereof), and so forth. These elements may be implemented in assemblerinstructions supported by processor(s) 602 or high-level languages, suchas, for example, C, that can be compiled into such instructions.

The permanent copy of the programming instructions may be placed intomass storage devices 606 in the factory, or in the field, through, forexample, a distribution medium (not shown), such as a compact disc (CD),or through communication interface 610 (from a distribution server (notshown)). That is, one or more distribution media having animplementation of the agent program may be employed to distribute theagent and program various computing devices.

The constitution of elements 602-612 are known, and accordingly will notbe further described.

FIG. 7 illustrates an example non-transitory computer-readable storagemedium having instructions configured to practice all or selectedaspects of the methods of FIG. 2-5; in accordance with variousembodiments of the present disclosure. As illustrated, non-transitorycomputer-readable storage medium 702 may include a number of programminginstructions 704. Programming instructions 704 may be configured toenable a device, e.g., computer 600, in response to execution of theprogramming instructions, to perform various operations of the variousflows of FIG. 2-5. In alternate embodiments, programming instructions704 may be disposed on multiple non-transitory computer-readable storagemedia 702 instead.

Referring back to FIG. 6, for one embodiment, at least one of processors602 may be packaged together with computational logic 622 configured topractice aspects of one of the flows of FIGS. 2-5. For one embodiment,at least one of processors 602 may be packaged together withcomputational logic 622 configured to practice one or more aspects ofone of the flows of FIGS. 2-5 to form a System in Package (SiP). For oneembodiment, at least one of processors 602 may be integrated on the samedie with computational logic 622 configured to practice aspects of oneof the flows of FIGS. 2-5. For one embodiment, at least one ofprocessors 602 may be packaged together with computational logic 622configured to practice aspects of one of the flows of FIGS. 2-5 to forma System on Chip (SoC). For at least one embodiment, the SoC may beutilized in, e.g., but not limited to, a computing tablet.

Thus, at least one non-transitory computer-readable storage medium mayhave a plurality of instructions configured to enable a computingdevice, in response to execution of the instructions by the computingdevice, to implement a DRM locker on the computing device. The DRMlocker may be configured to receive and store a first DRM license or keyof a first DRM protected content of a first content provider in the DRMlocker; and receive and store a second DRM license or key of a secondDRM protected content of a second content provider in the DRM locker.Further, on presentation of an associated locker key, the DRM locker mayrespond to a request for the first or second DRM license or key with thecorresponding first or second DRM license or key, to enable consumptionof the corresponding first or second DRM protected content using thecomputing device.

In embodiments, receive and store of the first and second DRM licensesmay include receive and store the first and second DRM licenses that areof different DRM license types. In embodiments, receive and store of thefirst and second DRM keys may include receive and store the and secondDRM keys that are of different DRM key types. In embodiments, receiveand store of the first and second DRM licenses or keys may includereceive and store the first and second DRM licenses or keys of the firstand second DRM protected content that are audio or video content. Inembodiments, receive and store of the first and second DRM licenses orkeys may include receive and store the first and second DRM licenses orkeys from the first and second content providers that are differentcontent providers. In embodiments, respond to a request for the first orsecond DRM license or key may include respond to a request for the firstor second DRM license or key by a DRM library or a media player of thecomputing device.

In embodiments, the instructions may be first instructions, and the atleast one computer-readable storage medium may further include secondinstructions, in response to execution by the computing device, enablethe computing device to provide information about the computing deviceto a DRM locker vendor to obtain the first instructions from the DRMlocker vendor. In embodiments, the instructions may be firstinstructions, and the at least one computer-readable storage medium mayfurther include second instructions, in response to execution by thecomputing device, enable the computing device to provide informationabout the DRM locker or the computing device to a content distributionsystem of the first content provider.

In embodiments, the computing device may be a selected one of asmartphone, a computing tablet, a laptop computer, a desktop computer, aPDA, a game player, a media player, a game console, or a set-top box.

Additionally, at least one non-transitory computer-readable storagemedium having a plurality of instructions configured to provide to acomputing device, in response to execution of the instructions by thecomputing device, to implement a DRM locker vendor service. The DRMlocker vendor service may be configured to provide a DRM locker and anassociated locker key to a client device. The DRM locker may beconfigured to receive and store DRM licenses or keys for a plurality ofDRM protected contents of a plurality of content providers. Onpresentation of the associated locker key, the DRM locker may respond toa request for a first DRM license or key with the first DRM license orkey, to enable consumption of a corresponding first DRM protectedcontent using the client device.

In embodiments, the DRM licenses or keys may include DRM licenses orkeys of a plurality of DRM license or key types. In embodiments, the DRMlocker vendor service may be further configured to provide theassociated locker key to an escrow service to escrow the associatedlocker key. In embodiments, the computing device and the client devicemay be remotely disposed from each other, and the DRM locker vendorservice may be configured to provide the DRM locker and the associatedlocker key to the client device via one or more networks coupling thecomputing device and the client device.

Further, a method may include receiving, by a computing device of anescrow service, from a DRM locker vendor service, a locker keyassociated with a DRM locker provided by the DRM locker vendor serviceto a first client device; and on presentation of required information,providing by the computing device, the locker key to a second clientdevice, different from the first client device, to enable the DRM lockerto be moved and used on the second client device. The DRM locker may beconfigured to receive and store DRM licenses or keys of a plurality ofDRM license or key types for a plurality of DRM protected contents of aplurality of content providers, on a selected one of the first or secondclient device where the DRM locker is installed, to enable consumptionof the DRM protected contents using the selected one of first or secondclient device.

In embodiments, the method may further includes receiving the requiredinformation, by the computing device, from the second client device. Inembodiments, the required information may include information about alicensee of the DRM locker.

Still further, an apparatus may include one or more servers; and acontent distribution system operated by the one or more servers. Thecontent distribution system may be configured to receive, from a clientdevice, a purchase order for a DRM protected content; determine whetherthe client device has a DRM locker; and on determination that the clientdevice has a DM locker, generate a local DRM license or key for the DRMprotected content, and provide the local DRM license or key to theclient device for storage in the DRM locker, and facilitate by the DRMlocker consumption of the DRM protected content using the client device.

In embodiments, the content distribution system may be furtherconfigured to provide the DRM protected content to the client device. Inembodiments, the content distribution system may be further configuredto, on determination that the client device does not have a DRM locker,generate a network DRM license or key for the DRM protected content,store the network DRM license or key in storage accessible to thecontent distribution system, and facilitate consumption of the DRMprotected content using the client device using the network DRM licenseor key.

In embodiments, the DRM locker may be configured to store a plurality oflocal DRM licenses or keys of a plurality of DRM license or key typesfor a plurality of DRM protected contents of a plurality of contentproviders.

Although specific embodiments have been illustrated and describedherein, it will be appreciated by those of ordinary skill in the artthat a wide variety of alternate and/or equivalent implementations maybe substituted for the specific embodiments shown and described, withoutdeparting from the scope of the embodiments of the present disclosure.This application is intended to cover any adaptations or variations ofthe embodiments discussed herein. Therefore, it is manifestly intendedthat the embodiments of the present disclosure be limited only by theclaims.

What is claimed is:
 1. An apparatus, comprising: a digital rightsmanagement (DRM) locker to manage DRM licenses or keys for DRM protectedcontents downloaded onto the apparatus from different content providers;wherein the DRM locker is transmitted from a server of a DRM lockervendor, has an associated locker key, and is configured to: receive andstore a first DRM license or key of a first DRM protected contentdownloaded onto the apparatus from a first content provider, in the DRMlocker, wherein the first DRM license or key is sent by the firstcontent provider on confirmation of the presence of the DRM locker tothe first content provider, by the apparatus; receive and store a secondDRM license or key of a second DRM protected content downloaded onto theapparatus from a second content provider, in the DRM locker, wherein thesecond DRM license or key is sent by the second content provider onconfirmation of the presence of the DRM locker to the second contentprovider, by the apparatus, wherein the first and second contentproviders are different content providers; and on presentation of theassociated locker key by a DRM library or media player of the apparatus,respond to a request of the corresponding DRM library or media playerfor the first or second DRM license or key, with the corresponding firstor second DRM license or key, to enable consumption of the correspondingdownloaded first or second DRM protected content, using the apparatus.2. The apparatus of claim 1, wherein the first and second DRM licensesare of different DRM license types.
 3. The apparatus of claim 1, whereinthe first and second DRM keys are of different DRM key types.
 4. Theapparatus of claim 1, wherein the first and second DRM protected contentare audio or video content.
 5. The apparatus of claim 1, wherein theapparatus is configured to provide information about the apparatus tothe DRM locker vendor to obtain the DRM locker, and the associatedlocker key of the DRM locker from the DRM locker vendor, wherein theassociated locker key of the DRM locker is particularized to theapparatus, based at least in part on some of the information about theapparatus provided.
 6. The apparatus claim 1, wherein the apparatus isfurther configured to provide information about the DRM locker and theapparatus to a content distribution system of the first content providerto confirm to the first content provider, presence of the DRM locker onthe apparatus.
 7. The apparatus of claim 1, wherein the apparatus is aselected one of a smartphone, a computing tablet, a laptop computer, adesktop computer, a personal digital assistant (PDA), a game player, amedia player, a game console, or a set-top box.
 8. An apparatus,comprising: one or more processors; and an escrow service to be operatedby the one or more processors to: receive, from a digital rightsmanagement (DRM) locker vendor service, differ from the escrow service,a locker key associated with a DRM locker provided by the DRM lockervendor service to a first client device; and on presentation of requiredinformation, provide the locker key to a second client device, differentfrom the first client device, to enable the DRM locker to be moved andused usable on the second client device, after the DRM locker has beenmoved from the first client device to the second client device; whereinthe DRM locker is configured to receive and store DRM licenses or keysof a plurality of DRM license or key types for a plurality of DRMprotected contents of a plurality of different content providers,downloaded onto a selected one of the first or second client devicewhere the DRM locker is installed, to enable consumption of thedownloaded DRM protected contents, using the selected one of first orsecond client device, wherein the DRM licenses or keys are sent by thedifferent content providers on confirmation of the presence of the DRMlocker to the content providers, by the selected one of the first orsecond client device.
 9. The apparatus of claim 8, wherein the escrowservice to further receive the required information from the secondclient device.
 10. The apparatus of claim 8, wherein the requiredinformation comprises information about a licensee of the DRM locker.11. At least one non-transitory computer-readable storage medium havinga plurality of instructions configured to provide to a computing device,in response to execution of the instructions by the computing device, acontent distribution system configured to: receive, from a clientdevice, a purchase order for a digital rights management (DRM) protectedcontent; determine whether the client device has a DRM locker providedto the client device by a DRM locker vendor, and the DRM locker issecured with an associated locker key; and on determination that theclient device has a DRM locker provided by the DRM locker vendor, andthe DRM locker is secured with an associated locker key, generate alocal DRM license or key for the DRM protected content, enabling the DRMprotected content to be downloaded and consumed onto the client device,and provide the local DRM license or key to the client device forstorage in the DRM locker, and for facilitation facilitate by the DRMlocker, consumption of the downloaded DRM protected content, using theclient device.
 12. The storage medium of claim 11, wherein the contentdistribution system is further configured to, on determination that theclient device does not have a DRM locker, generate a network DRM licenseor key for the DRM protected content, store the network DRM license orkey in storage accessible to the content distribution system, andfacilitate consumption of the DRM protected content using the clientdevice, using the network DRM license or key.
 13. The storage medium ofclaim 11, wherein the DRM locker is configured to store a plurality oflocal DRM licenses or keys of a plurality of DRM license or key typesfor a plurality of DRM protected contents of a plurality of contentproviders.